-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build: Don't auto-trigger CI on release PRs #23198
Conversation
- version-prerelease-from-** | ||
- version-patch-from-** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't need this as it should already be covered by "pull_request_target" > "synchronize", and removing these makes sure the "merged" workflow doesn't trigger unnecessarily.
@@ -56,7 +54,7 @@ jobs: | |||
trigger-pr-tests: | |||
runs-on: ubuntu-latest | |||
needs: get-branch | |||
if: github.event_name == 'pull_request_target' && ((github.event.pull_request.draft == false || contains(github.event.pull_request.labels.*.name, 'ci:pr')) && !contains(github.event.pull_request.labels.*.name, 'ci:merged') && !contains(github.event.pull_request.labels.*.name, 'ci:daily')) | |||
if: github.event_name == 'pull_request_target' && (((github.event.pull_request.draft == false && !contains(github.event.pull_request.labels.*.name, 'release')) || contains(github.event.pull_request.labels.*.name, 'ci:pr')) && !contains(github.event.pull_request.labels.*.name, 'ci:merged') && !contains(github.event.pull_request.labels.*.name, 'ci:daily')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trigger PR tests if:
- is "pull_request_target" event
- AND
- (not draft
- AND not "release")
- OR has "ci:pr" label
- AND don't have "ci:merged"
- AND don't have "ci:daily"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
Build: Don't auto-trigger CI on release PRs (cherry picked from commit 1d61076)
What I did
We don't want to trigger CI on any updates to release PRs because they update frequently and it's a waste to run CI before we actually are ready for the release process.
Now the Releaser have to manually add the ci:daily label to trigger CI on changes.
How to test
Checklist
MIGRATION.MD
Maintainers
make sure to add the
ci:merged
orci:daily
GH label to it.["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]